Make toList() safer on Collections with size 1 #5567
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's possible for library code to define a Collection whose size property is one, but producing an iterator without any next element. This is probably some kind of mistake, but it's also very hard for a user of that library to deal with the error that toList() generates under those circumstances. If size is 1, conditionally generate an empty list if the initial iterator has no next element, consistently with other collection snapshotters.